Monitoring user activity on a mobile device

ABSTRACT

Monitoring user activity on a mobile device is described. In one aspect, video content is received and played to a user of the mobile device. The monitoring activity detects an interruption of playback of the video content and determines an event associated with the interruption. The event is stored in the mobile device and communicated to a remote device.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of co-pending U.S. patent applicationSer. No. 12/823,116, filed 24 Jun. 2010, entitled “Monitoring UserActivity on a Mobile Device,” the entirety of which is herebyincorporated by reference for all intents and purposes.

BACKGROUND

The rapid increase in mobile device usage as well as the increase infunctionality offered by mobile devices has created a variety of newapplications for these devices. Mobile device users are now relying onmobile devices for more than telephone conversation and communicatingvia text messages. Current mobile devices have sufficient computingresources to perform a variety of tasks, such as displaying videocontent stored on the mobile device or streamed to the device through awireless communication link.

As the number and types of tasks performed on mobile devices increase,mobile service providers and other organizations seek to providevaluable content and services to the mobile device users. To identifyuser interests and preferences regarding content, such as video content,it is desirable to monitor user activity on the mobile device. Forexample, organizations providing video content to mobile devices benefitfrom knowing the types of content and viewing habits of mobile deviceusers. Therefore, it is desirable to offer a system for monitoring useractivity with respect to various types of content to provide an improveduser experience.

SUMMARY

The described systems and methods relate to monitoring and reportinguser activity associated with a mobile device. In a specificimplementation, the mobile device receives video content from a datasource and displays that video content to a user of the mobile device.The mobile device detects an interruption of playback of the videocontent and determines an event associated with that interruption.Information related to the event is stored in the mobile device andcommunicated to a remote device.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

DESCRIPTION OF THE FIGURES

In the Figures, the left-most digit of a component reference numberidentifies the particular Figure in which the component first appears.

FIG. 1 shows an exemplary environment capable of implementing thesystems and methods described herein.

FIG. 2 is a block diagram showing various components of an exemplarymobile device, according to one embodiment.

FIG. 3 shows an exemplary procedure for monitoring usage of a mobiledevice, according to one embodiment.

FIG. 4 shows an exemplary procedure for logging and uploading mobiledevice usage information, according to one embodiment.

FIG. 5 shows an exemplary log file header, according to one embodiment.

FIG. 6 shows an exemplary session header, according to one embodiment.

FIG. 7 shows an exemplary log file, according to one embodiment.

FIG. 8 shows exemplary event data associated with a channel change ortune event, according to one embodiment.

FIG. 9 shows exemplary data associated with a content recording event,according to one embodiment.

FIG. 10 shows exemplary data associated with a playback of recordedcontent event, according to one embodiment.

FIG. 11 shows exemplary data associated with a transition event fromvideo playback to another mode of operation, according to oneembodiment.

FIG. 12 shows exemplary data associated with a power state change event,according to one embodiment.

FIG. 13 shows exemplary data associated with tracking of displaycharacteristics, according to one embodiment.

FIG. 14 shows exemplary data associated with tracking of signal quality,according to one embodiment.

FIG. 15 is a block diagram showing an exemplary computing device,according to one embodiment.

DETAILED DESCRIPTION

Overview

The systems and methods described herein relate to the monitoring andreporting usage of a mobile device. These systems and methods monitoruser habits when viewing video content on the mobile device. Inparticular, when the viewing of video content is interrupted, a log fileis updated indicating the reason for stopping the video playback. Thesereasons include, for example, user selection of different video content,activating a different application on the mobile device, loss of power,loss of a communication link to the video data source, and the like. Theinformation collected in the log file is communicated to a server orsimilar device for analysis of user viewing habits and relatedinformation.

As used herein, a mobile device may include a cellular phone, smartphone, handheld computer, tablet computer, laptop computer, portablegaming device, portable entertainment device, or other portable devicecapable of performing some or all of the functions discussed herein. Asfurther used herein, a mobile device may also be referred to as a“portable computing device”. Although particular examples discussedherein relate to the display of video content on a mobile device, thepresent invention is applicable to the handling of any type of contentor other data received by the mobile device.

An Exemplary System for Monitoring Usage of a Mobile Device

FIG. 1 shows an exemplary environment 100 capable of implementing thesystems and methods described herein. A satellite headend 102communicates various types of data to a satellite 104. As discussedherein, satellite headend 102 communicates video content (e.g., movies,television programs, sporting events and music videos) to one or moredata retransmission points 120. Data retransmission point 120 is capableof communicating with satellite 104 as well as multiple mobile devices106. Satellite headend 102 may also communicate the same video contentto other devices (not shown) simultaneously via satellite 104.Additionally, satellite headend 102 may communicate video content tomobile devices 106 through other communication paths, such as via otheraccess points of the type discussed below.

Satellite headend 102 receives various types of content from multiplesources. In the example of FIG. 1, satellite headend 102 receives videocontent from a video data store 108 and receives additional data from adata source 110. Data source 110 may provide video content, audiocontent, or any other type of data to satellite headend 102. Data source110 can be located proximate satellite headend 102 or at a distantgeographic location.

Mobile device 106 receives video content and other data from dataretransmission point 120. In a particular embodiment, dataretransmission point 120 communicates with mobile device 106 via awireless communication link at approximately 700 MHz. Dataretransmission point 120 is located proximate a transmission tower orother transmission system capable of transmitting data to multiplemobile devices 106. Data retransmission point 120 also includes asatellite receiver capable of receiving video content and other datafrom one or more satellites 104.

In a particular embodiment, mobile device 106 includes an applicationprogram that is capable of rendering and displaying the received videocontent on the mobile device's display screen. This application allowsthe user of mobile device 106 to watch television programs, movies, andsimilar content on the mobile device. In a particular implementation,the user selects among multiple video content programs based on thevideo content available for communication to mobile device 106 throughsatellite 104 and data retransmission point 120.

In a particular embodiment, mobile device 106 communicates back tosatellite headend 102 via a metering collector 122. Metering collector122 receives data from multiple mobile devices 106 and forwards thatdata to satellite headend 102 and/or a server 116. Additionally,metering collector 122 may store data received from one or more mobiledevices 106. Mobile device 106 communicates with metering collector 122via a data communication network (or “back channel”) such as 3G (3rdgeneration) or WiFi (a wireless networking technology). 3G defines afamily of standards for mobile communications. WiFi is defined as awireless local area network (WLAN) based on IEEE (Institute ofElectrical and Electronics Engineers) 802.11 standards. This channel isused to communicate user commands and other information from mobiledevice 106 to metering collector 122. In this embodiment, mobile devices106(1) and 106(2) utilize the 3G data communication network, which isaccessed via a 3G access point 112. Mobile device 106(3) uses a WiFidata communication network, and accesses that network via a WiFi accesspoint 114. WiFi access point 114 and 3G access point 112 are coupled tometering collector 122 via one or more data communication networks, suchas local area networks (LANs), wide area networks (WANs) and theInternet. Similarly, metering collector 122 is coupled to satelliteheadend 102 and server 116 via one or more data communication networksor other communication links.

In addition to the communication of data from mobile device 106 tometering collector 122 via access points 112 and 114, the meteringcollector may use this same communication path to communicate videocontent and other data to the mobile device.

Mobile devices 106 communicate various user viewing habits andactivities to metering collector 122. As shown in FIG. 1, server 116 iscoupled to satellite headend 102 and metering collector 122 such thatserver 116 receives user viewing information from mobile devices 106 viathe satellite headend and/or the metering collector. In alternateembodiments, server 116 receives user viewing information directly fromthe mobile devices 106 (e.g., via a 3G or WiFi communication link).Server 116 stores the user viewing information received from mobiledevices 106 in a user data store 118, such as a database. Server 116represents any type of computing device capable of receiving and storingdata as discussed herein. In one embodiment, server 116 is locatedproximate satellite headend 102 or metering collector 122. In alternateembodiments, server 116 is positioned a significant distance from bothsatellite headend 102 and metering collector 122, and is configured tocommunicate with the satellite headend or metering collector via one ormore data communication networks.

Although the described environment 100 distributes video content tomobile devices 106 via satellite, alternate embodiments may distributevideo content via any communication mechanism. For example, videocontent and other data can be communicated to data retransmission point120 via a wired or wireless communication link with a data communicationnetwork, such as the Internet. In particular embodiments, dataretransmission point 120 receives video content and other data frommultiple sources, such as satellite 104 as well as a wired or wirelesscommunication link to a data communication network.

FIG. 2 is a block diagram showing various components of exemplary mobiledevice 106, according to one embodiment. Mobile device 106 includes aprocessor 202, a memory 204 and a communication module 206. Processor202 executes various instructions to implement the functionalitydiscussed herein. Memory 204 stores these instructions as well as otherdata used by processor 202 and other modules contained in mobile device106. Communication module 206 allows mobile device 106 to communicatewith other devices and systems, such as data retransmission point 120,3G access point 112 and WiFi access point 114 shown in FIG. 1.

Mobile device 106 also includes a display 208 and a user interface 212.Display 208 is used to present video content and other information to auser of the mobile device. In a particular embodiment, display 208 is atouch-sensitive display such that the display can also function toreceive user input. User interface 212 receives information from theuser (e.g., via touch-sensitive display 208 and various buttons,switches, and other input controls) and presents options and otherinformation to the user via the display. User interface 212 allows theuser to control the operation of mobile device 106, including theexecution of various applications and other functions contained in themobile device.

Applications 210 in mobile device 106 perform various operations usingother components of the mobile device. Example applications 210 includea video content player, a telephone application, a web browserapplication, a mobile device configuration application, and the like. Alog file 214 stores information related to user viewing habits, useractivities, signal strength and GPS location data associated with mobiledevice 106. Additional details regarding the use of log file 214 areprovided herein. A GPS (Global Positioning System) module 216 identifieslocation coordinates associated with the current position of mobiledevice 106. These location coordinates are stored in log file 214 alongwith other data associated with mobile device 106. In alternateembodiments, module 216 uses other location identification procedures todetermine the location of mobile device 106, such as cell towertriangulation or WiFi positioning.

An Exemplary Procedure for Monitoring Usage of a Mobile Device

FIG. 3 shows an exemplary procedure 300 for monitoring usage of a mobiledevice, according to one embodiment. Initially, a satellite headendreceives video content (block 302). As discussed above, the satelliteheadend can receive video content from a variety of sources, such asdata source 110 and stored video data 108. The satellite headendprocesses the video content and transmits the processed video content toa satellite (block 304), such as satellite 104 shown in FIG. 1. Thisprocessing may include compressing the video data prior to communicationor reformatting the video content for proper display on differentdisplay screen sizes, resolution and aspect ratio. Procedure 300continues as the satellite receives the video content from the head endand re-transmits the video content to a data retransmission point (block306), such as data retransmission point 120 shown in FIG. 1.

A mobile device (such as mobile device 106 shown in FIG. 1) receives thevideo content from the data retransmission point and displays the videocontent to a user of the mobile device (block 308). In a particularembodiment, playback of the video content displayed to the user of themobile device is under the control of the user. The user is able tonavigate to different parts of the video content, pause playback, andterminate playback of the video content. The mobile device monitors useractivity and collects other information (block 310), such as GPSlocation information, signal strength and so forth. Additionally, themobile device monitors user activity and device activity for anyinterruption in the display or playback of the video content. Thisinterruption may be the result of a variety of factors, such as the userstopping playback, changing video channels, or launching a differentapplication. Further, the interruption may be the result of a loss ofcommunication with the data retransmission point, mobile device batteryfailure, and so forth.

The mobile device stores the user activity data and other information ina log file (block 312) within the mobile device. Finally, the mobiledevice communicates the user activity data and other information fromthe log file to a metering collector, a server, or the satellite headendat periodic intervals (block 314). In one embodiment, log file data iscommunicated to the headend at regular intervals, such as every fiveseconds. In other embodiments, log file data is communicated to theheadend based on the amount of data stored in the log file (e.g., whenthe log file has a certain number of data entries or when the log fileis 50% full).

In an alternate embodiment, a first communication device receives thevideo content from the data retransmission point, as discussed abovewith respect to FIG. 3. The first communication device does not play thereceived video content. Instead, the first communication devicecommunicates the received video content to a mobile device, which playsthe received video content. The first communication device monitors useractivity on the mobile device, as reported back to the firstcommunication device by the mobile device. The first communicationdevice stores the user activity data and other information in a log fileand communicates that data and information to a metering collector, aserver, or a satellite headend at periodic intervals.

FIG. 4 shows an exemplary procedure 400 for logging and uploading mobiledevice usage information, according to one embodiment. Initially, themobile device detects user activity, signal strength and GPS locationdata (block 402). The various information collected regarding useractivity, signal strength and GPS location is stored in the log file atperiodic intervals, such as every five seconds. Procedure 400 continuesby determining whether the current time is appropriate for storing datato the log file (block 404). If not, the procedure branches to block 410to determine whether upload criteria has been met, as discussed below.

If block 404 indicates that data is to be logged, the procedure nextdetermines whether storage space exists in the log file for the new data(block 406). If there is insufficient space in the log file, theprocedure branches to block 410 without storing the data in the logfile. If there is space in the log file to store the data, the mobiledevice stores the user activity, signal strength and GPS location datain the log file (block 408). The procedure continues to block 410, whichdetermines whether criteria is met for uploading the log file data to aserver or other device (block 412). In a particular embodiment, thisupload criteria includes uploading the log file data when 1) the totalnumber of files stored on the mobile device exceeds 50% of the maximumallowed files; or 2) the last upload of log file data occurred more thanone week ago. If the upload criteria is not met at block 410, theprocedure returns to block 402, where the mobile device continuesdetecting user activity, signal strength and GPS location data.

If the upload criteria is met, the mobile device uploads the log filedata to a server or other device/system (block 412). For example, themobile device may upload the log file data directly to server 116 (FIG.1), upload the log file data to the server through metering collector122, or upload the log file data to the server via satellite headend102. Server 116 stores the log file data in user data store 118. In aparticular embodiment, the log file data is communicated using the HTTPS(Hypertext Transfer Protocol Secure) protocol and utilizes the standardPOST mechanism to submit the log file data to the identified server.

In alternate embodiments, the mobile device uploads the log file data toany remote device capable of storing the log file data. This remotedevice may be a server (as discussed herein) or any other computingdevice capable of communicating with the mobile device and receiving thelog file data. The remote device may store the log file data itself orcommunicate the data to another device that stores the log file data forfuture reference or analysis.

FIG. 5 shows an exemplary log file header 500, according to oneembodiment. Log file header 500 includes a unique identifier assigned toeach log file. In a particular implementation, the unique identifier isan integer number. Log file header 500 also contains an indicator of thedate and time the log file was created, and a version associated withthe reporting structure. The version is particularly useful whendifferent log file versions are used over a period of time. Log fileheader 500 also includes a device manufacture identifier and a deviceidentifier. The device manufacture identifier indicates the manufactureror vendor of the mobile device, and the device identifier is a uniqueidentifier associated with the particular mobile device. Log file header500 further contains a firmware version and an application version. Thefirmware version indicates the version of firmware installed in theparticular mobile device, and the application version indicates theversion of the video player application executing on the mobile device.

FIG. 6 shows an exemplary session header 600, according to oneembodiment. Each logging session has a session header at the beginningand ending of the logging session. Session header 600 includes a sessionheader type, a time and a version. The session header type indicateswhether session header 600 is associated with the start of a loggingsession or with the end of a logging session. The time parameter insession header 600 indicates the time when the session header wascreated. The version indicates a software version associated with theapplication that monitors user activity and other data.

Session header 600 also includes a signal strength, a signal-to-noiseratio (SNR) and an RS error. The signal strength is associated with thestrength of the communication link between the mobile device and asatellite communicating video content to the mobile device. The SNR isalso associated with the communication link between the mobile deviceand the satellite. The RS error refers to the Reed-Solomon error, whichincludes codes used to correct various symbol errors.

Session header 600 further includes a battery charge indicator, abattery charge level and a GPS location. The battery charge indicator isset depending on whether the battery in the mobile device is currentlycharging. The battery charge level indicates the percentage of batterylife remaining. The GPS location identifies the current geographiclocation of the mobile device.

FIG. 7 shows an exemplary log file 700, according to one embodiment.FIG. 7 illustrates a portion of log file 700 associated with twodifferent sessions (labeled “Session 1” and “Session 2). Log file 700includes a log file header 702 containing the information discussedabove with respect to FIG. 5. A session 1 header 704 indicates the startof Session 1, and is followed by multiple events that occur during thatsession (i.e., “Event 1” and “Event 2” identified by reference numerals706 and 708, respectively). A particular session may include any numberof events. Another session 1 header 710 indicates the end of Session 1.A session 2 header 712 indicates the start of Session 2, and is followedby session 2 event 1 (reference numeral 714) and additional events thatoccur in session 2. This same data structure is followed for theremaining sessions stored in log file 700.

FIG. 8 shows exemplary event data 800 associated with a channel changeor channel tuning event, according to one embodiment. This event occurswhen a user of the mobile device changes to a different televisionchannel or other content channel, thereby indicating that the user is nolonger watching the previous video content. This event information iscollected to determine how long the user viewed the previous videocontent and what video content they selected as a result of the channelchange.

Event data 800 includes an event type that indicates a channel change, aservice ID associated with the service being used by the mobile device,and a service name related to the name of the channel the user isviewing. Event data 800 also includes a service tune time indicating thetime required to begin displaying video content to the user, and acontent type indicating whether the video content is broadcaststreaming, broadcast file delivery, or some other type of content. Eventdata 800 further includes a start time and an end time associated withthe video content, and an event end transition that indicates the reasonfor the channel change event. The reason for the channel change eventmay be a user channel change command, a change in power state (mobiledevice powered off or switched to standby mode), the user activated adifferent application on the mobile device (such as a phoneapplication), loss of communication signal by the mobile device, or auser command to stop or exit the video display application. The reasonfor the channel change event is valuable in analyzing user viewinghabits for various types of video content in different situations. Eventdata 800 also includes SNR data, RS error data and GPS positioninformation, as discussed above with respect to FIG. 6.

FIG. 9 shows exemplary event data 900 associated with a contentrecording event, according to one embodiment. Event data 900 includes anevent type identifying the event as a content recording event and aservice ID similar to the service ID shown in FIG. 8. Event data 900also includes a time of recording field indicating the recording starttime for the recording event. Additionally, event data 900 includes SNR,RS error and GPS position information of the type discussed herein.

FIG. 10 shows exemplary event data 1000 associated with a playback ofrecorded content event, according to one embodiment. Event data 1000includes an event type identifying the event as a recorded contentplayback event and a service ID similar to the service ID discussedabove. Event data 1000 also includes a time of recording fieldindicating the start time for the recorded content, and a time ofplayback start indicating the time at which the user initiated theplayback event. A trick play event indicator identifies whether the userhas activated any “trick play events”, such as pause, instant replay, orrewind during playback of the content.

Event data 1000 further includes a time field that indicates atime-based position within the content in relation to real-time viewingof the content. Trick play date/time data indicates the time that thetrick play command occurred, and a playback end date/time identifies theend of the playback event. Additionally, event data 1000 includes SNR,RS error and GPS position information of the type discussed herein.

FIG. 11 shows exemplary event data 1100 associated with a transitionevent from video playback to another mode of operation, according to oneembodiment. Event data 1100 includes an event type identifying the eventas a transition away from the video playback mode. A date and time fieldindicates the time at which the transition occurred, and audio mode dataindicates the audio mode of the mobile device, such as mobile devicespeakers are on, headphones are installed in the mobile device, or thedevice audio is muted. Event data 1100 also includes a screen size modethat indicates whether the mobile device is operating in full screenmode or some other display mode. A controls field indicates whether anyavailable controls have been implemented, such as parental controls orother restrictions on operation of the mobile device. Additionally,event data 1100 includes SNR and RS error information of the typediscussed herein.

FIG. 12 shows exemplary event data 1200 associated with a power statechange event, according to one embodiment. Event data 1200 includes anevent type identifying the event as a change in the power state of themobile device, such as powering off the mobile device or changing thepower state to standby. Event data 1200 also includes state informationthat indicates the current state of the mobile device. These statesinclude powered on and connected to a wireless data network, poweredoff, operating on battery and operating on external power. Additionally,event data 1200 includes SNR, RS error and GPS position information ofthe type discussed herein.

FIG. 13 shows exemplary event data 1300 associated with tracking ofdisplay characteristics, according to one embodiment. Event data 1300includes an event type identifying the event as tracking one or moredisplay characteristics of the mobile device. Start time and end timedata is associated with the time period of tracking the displaycharacteristics. Event data 1300 includes a display cover that indicateswhat item is being displayed on the mobile device, such as an electronicprogram guide or a device menu. An ID field in event data 1300 isassociated with menu commands and display windows, such as a channellist, program list on a particular channel, specific programinformation, settings menu, channel menu, or channel scan. Additionally,event data 1300 includes SNR, RS error and GPS position information ofthe type discussed herein.

FIG. 14 shows exemplary event data 1400 associated with tracking ofsignal quality, according to one embodiment. Event data 1400 includes anevent type identifying the event as tracking signal quality associatedwith the communication link used by the mobile device. A time fieldindicates the time at which the signal quality event occurred. Eventdata 1400 also includes SNR, RS error and GPS position information ofthe type discussed herein. In a particular implementation, the signalquality tracking event is logged to the log file every five seconds.

FIG. 15 is a block diagram showing an exemplary computing device 1500,according to one embodiment. Computing device 1500 may be used toperform various procedures, such as those discussed herein. Computingdevice 1500 can function as a server, a client, a worker node, or anyother computing entity. Computing device 1500 can be any of a widevariety of computing devices, such as a desktop computer, a notebookcomputer, a server computer, a handheld computer, and the like.

Computing device 1500 includes one or more processor(s) 1502, one ormore memory device(s) 1504, one or more interface(s) 1506, one or moremass storage device(s) 1508, one or more Input/Output (I/O) device(s)1510, and a display device 1528 all of which are coupled to a bus 1512.Processor(s) 1502 include one or more processors or controllers thatexecute instructions stored in memory device(s) 1504 and/or mass storagedevice(s) 1508. Processor(s) 1502 may also include various types ofcomputer-readable media, such as cache memory.

Memory device(s) 1504 include various computer-readable media, such asvolatile memory (e.g., random access memory (RAM)) 1514 and/ornonvolatile memory (e.g., read-only memory (ROM) 1516). Memory device(s)1504 may also include rewritable ROM, such as Flash memory.

Mass storage device(s) 1508 include various computer readable media,such as magnetic tapes, magnetic disks, optical disks, solid statememory (e.g., Flash memory), and so forth. As shown in FIG. 15, aparticular mass storage device is a hard disk drive 1524. Various drivesmay also be included in mass storage device(s) 1508 to enable readingfrom and/or writing to the various computer readable media. Mass storagedevice(s) 1508 include removable storage 1526 and/or non-removablemedia.

I/O device(s) 1510 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 1500.Example I/O device(s) 1510 include cursor control devices, keyboards,keypads, microphones, monitors or other display devices, speakers,printers, network interface cards, modems, lenses, CCDs or other imagecapture devices, and the like.

Display device 1528 includes any type of device capable of displayinginformation to one or more users of computing device 1500. Examples ofdisplay device 1528 include a monitor, display terminal, videoprojection device, and the like.

Interface(s) 1506 include various interfaces that allow computing device1500 to interact with other systems, devices, or computing environments.Example interface(s) 1506 include any number of different networkinterfaces 1520, such as interfaces to local area networks (LANs), widearea networks (WANs), wireless networks, and the Internet. Otherinterfaces include user interface 1518 and peripheral device interface1522.

Bus 1512 allows processor(s) 1502, memory device(s) 1504, interface(s)1506, mass storage device(s) 1508, and I/O device(s) 1510 to communicatewith one another, as well as other devices or components coupled to bus1512. Bus 1512 represents one or more of several types of busstructures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, andso forth.

For purposes of illustration, programs and other executable programcomponents are shown herein as discrete blocks, although it isunderstood that such programs and components may reside at various timesin different storage components of computing device 1500, and areexecuted by processor(s) 1502. Alternatively, the systems and proceduresdescribed herein can be implemented in hardware, or a combination ofhardware, software, and/or firmware. For example, one or moreapplication specific integrated circuits (ASICs) can be programmed tocarry out one or more of the systems and procedures described herein.

CONCLUSION

Although the systems and methods for monitoring and reporting usage of amobile device have been described in language specific to structuralfeatures and/or methodological operations or actions, it is understoodthat the implementations defined in the appended claims are notnecessarily limited to the specific features or actions described.Rather, the specific features and operations of mobile device monitoringand usage reporting are disclosed as exemplary forms of implementing theclaimed subject matter.

What is claimed is:
 1. A method implemented on a mobile device, themethod comprising: receiving video content from a data source; playingthe received video content to a user of the mobile device; detecting aninterruption of playing the received video content; determining an eventassociated with the interruption; storing the event associated with theinterruption in the mobile device; and communicating the eventassociated with the interruption to a remote device.